Add TLS scanner job to csi-operator for AWS EBS - #82134
Conversation
|
Note Reviews pausedIt looks like this branch is under active development. To avoid overwhelming you with review comments due to an influx of new commits, CodeRabbit has automatically paused this review. You can configure this behavior by changing the Use the following commands to manage reviews:
Use the checkboxes below for quick actions:
WalkthroughCSI operator CI configurations add the ChangesTLS scanner CI integration
Estimated code review effort: 2 (Simple) | ~10 minutes Possibly related PRs
Suggested labels: Suggested reviewers: 🚥 Pre-merge checks | ✅ 15✅ Passed checks (15 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
openshift-ci
Bot
added
the
approved
|
/pj-rehearse pull-ci-openshift-csi-operator-main-tls-scanner-aws-ebs |
|
@RomanBednar: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
/pj-rehearse pull-ci-openshift-csi-operator-release-4.23-tls-scanner-aws-ebs |
|
@RomanBednar: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
/pj-rehearse pull-ci-openshift-csi-operator-main-tls-scanner-aws-ebs |
|
@RomanBednar: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
/pj-rehearse pull-ci-openshift-csi-operator-main-tls-scanner |
|
/pj-rehearse pull-ci-openshift-csi-operator-release-4.23-tls-scanner |
|
@RomanBednar: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
1 similar comment
|
@RomanBednar: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
/pj-rehearse pull-ci-openshift-csi-operator-release-5.0-tls-scanner |
|
@RomanBednar: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
/pj-rehearse pull-ci-openshift-csi-operator-release-5.0-tls-scanner |
|
@RomanBednar: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
/pj-rehearse pull-ci-openshift-csi-operator-release-4.23-tls-scanner |
|
@RomanBednar: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
/pj-rehearse pull-ci-openshift-csi-operator-main-tls-scanner |
|
@RomanBednar: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
c27b495 to
0dc6848
Compare
openshift-ci
Bot
removed
the
approved
Add an optional, manually-triggered TLS scanner presubmit job (tls-scanner-aws-ebs) to the csi-operator CI configuration for main, release-4.23, release-5.0, and release-5.1 branches. The job reuses the openshift-e2e-aws-csi workflow to provision an AWS cluster with the built-in EBS CSI driver, then overrides the test phase to run tls-scanner-run against the openshift-cluster-csi-drivers namespace. Scanner resources are set to 1 CPU / 1Gi to fit CI cluster node capacity. Triggered via `/test tls-scanner-aws-ebs`.
0dc6848 to
e26da2d
Compare
|
/pj-rehearse pull-ci-openshift-csi-operator-release-4.23-tls-scanner-aws-ebs pull-ci-openshift-csi-operator-main-tls-scanner-aws-ebs |
|
@RomanBednar: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
openshift-ci
Bot
added
the
approved
|
[REHEARSALNOTIFIER]
A total of 224 jobs have been affected by this change. The above listing is non-exhaustive and limited to 25 jobs. A full list of affected jobs can be found here Interacting with pj-rehearseComment: Once you are satisfied with the results of the rehearsals, comment: |
|
/pj-rehearse pull-ci-openshift-csi-operator-release-4.23-tls-scanner-aws-ebs |
|
@RomanBednar: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
|
/retest |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: rhrmo, RomanBednar The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
@RomanBednar: The label(s) DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
/pj-rehearse ack |
|
@RomanBednar: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
openshift-merge-bot
Bot
added
the
rehearsals-ack
|
@RomanBednar: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel. |
Add TLS_13_ENABLE_TLS_ADHERENCE, TLS_13_TLS_ADHERENCE_POLICY env vars and tls-13 step ref to tls-scanner-aws-ebs test in csi-operator configs for main, release-4.23, release-5.0, and release-5.1. This follows the pattern established in PR openshift#81917 for GCP Filestore and is a followup to PR openshift#82134 which added the base TLS scanner test.
Add an optional, manually-triggered TLS scanner presubmit job (tls-scanner-aws-ebs) to the csi-operator CI configuration for main, release-4.23, release-5.0, and release-5.1 branches. The job reuses the openshift-e2e-aws-csi workflow to provision an AWS cluster with the built-in EBS CSI driver, then overrides the test phase to run tls-scanner-run against the openshift-cluster-csi-drivers namespace. Scanner resources are set to 1 CPU / 1Gi to fit CI cluster node capacity. Triggered via `/test tls-scanner-aws-ebs`.
Add TLS_13_ENABLE_TLS_ADHERENCE, TLS_13_TLS_ADHERENCE_POLICY env vars and tls-13 step ref to tls-scanner-aws-ebs test in csi-operator configs for main, release-4.23, release-5.0, and release-5.1. This follows the pattern established in PR openshift#81917 for GCP Filestore and is a followup to PR openshift#82134 which added the base TLS scanner test.
2 participants
Summary
tls-scanner-aws-ebs) to csi-operator for main, release-4.23, release-5.0, and release-5.1Summary by CodeRabbit
Adds an optional, manually triggered
tls-scanner-aws-ebspresubmit job to thecsi-operatorCI configuration formain,release-4.23,release-5.0, andrelease-5.1. The job uses thetls-scanner-toolbase image and reuses theopenshift-e2e-aws-csiworkflow to runtls-scanner-runagainst theopenshift-cluster-csi-driversnamespace on theopenshift-org-awscluster profile (with OLM-related dependencies/env vars omitted since AWS EBS CSI is platform-built). It is invoked via/test tls-scanner-aws-ebs, and job definitions are generated viamake jobs.Rehearsal runs were requested for the TLS scanner job(s) on
main,release-4.23, andrelease-5.0, including both the driver-specifictls-scanner-aws-ebsname and the shortertls-scannervariant.